-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove Opcode Validation When Specifying a RelatedActivityId #38347
Conversation
I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks Brian!
Hello @brianrob! Because this pull request has the p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (
|
…38347) * Remove opcode validation when specifying relatedActivityId. * Remove test that is no longer needed.
…38347) * Remove opcode validation when specifying relatedActivityId. * Remove test that is no longer needed.
…38347) * Remove opcode validation when specifying relatedActivityId. * Remove test that is no longer needed.
…38347) * Remove opcode validation when specifying relatedActivityId. * Remove test that is no longer needed.
…38347) * Remove opcode validation when specifying relatedActivityId. * Remove test that is no longer needed.
…38347) * Remove opcode validation when specifying relatedActivityId. * Remove test that is no longer needed.
…38347) * Remove opcode validation when specifying relatedActivityId. * Remove test that is no longer needed.
…38347) * Remove opcode validation when specifying relatedActivityId. * Remove test that is no longer needed.
…38347) * Remove opcode validation when specifying relatedActivityId. * Remove test that is no longer needed.
…38347) * Remove opcode validation when specifying relatedActivityId. * Remove test that is no longer needed.
…38347) * Remove opcode validation when specifying relatedActivityId. * Remove test that is no longer needed.
…38347) * Remove opcode validation when specifying relatedActivityId. * Remove test that is no longer needed.
…38347) * Remove opcode validation when specifying relatedActivityId. * Remove test that is no longer needed.
…38347) * Remove opcode validation when specifying relatedActivityId. * Remove test that is no longer needed.
…38347) * Remove opcode validation when specifying relatedActivityId. * Remove test that is no longer needed.
…38347) * Remove opcode validation when specifying relatedActivityId. * Remove test that is no longer needed.
…38347) * Remove opcode validation when specifying relatedActivityId. * Remove test that is no longer needed.
…38347) * Remove opcode validation when specifying relatedActivityId. * Remove test that is no longer needed.
Fixes #38223.
The existing Opcode validation is overly strict, and isn't required by any of the logging systems that we support. There are some semantics defined on the consumption side for particular opcodes, but that doesn't preclude use of additional opcodes.
Right now, WCF client events are broken because they use a wider set of opcodes when specifying a RelatedActivityID.
cc: @mconnew